Tree

There is a problem

1000 entries with tree-preservation-order field must match the reference field in the tree preservation order

1499

reference: 581-tree-1
name: 1499
tree-preservation-order: undefined
581-tpo-1
uprn
address-text
point: POINT (-0.971585 50.866690)
geometry: MULTIPOLYGON (((-0.971514 50.866682,-0.971517 50.866696,-0.971527 50.866709,-0.971543 50.866719,-0.971562 50.866725,-0.971584 50.866728,-0.971606 50.866726,-0.971626 50.866719,-0.971642 50.866710,-0.971653 50.866697,-0.971656 50.866683,-0.971653 50.866669,-0.971643 50.866657,-0.971628 50.866647,-0.971608 50.866640,-0.971586 50.866638,-0.971564 50.866640,-0.971544 50.866646,-0.971528 50.866656,-0.971518 50.866668,-0.971514 50.866682)))
notes
felled-date
entry-date: 2026-08-06
start-date
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The tree guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that affects this tree.

Example: TPO1

This diagram shows the relationship between the tree preservation order dataset and the tree dataset. The reference value from your tree preservation order dataset needs to match the tree-preservation-order value in your tree dataset.

How to improve East Hampshire District Council’s data

Fix the errors indicated
Use the check service to make sure the data meets the standard
Publish the updated data on the endpoint URL